The Groups Grid on the Splash Page

The splash page is the first page that displays in the topic pane when the help set launches initially. Since 2026.1, it presents a Groups Grid: a responsive grid of entry-point cards built from your project's groups and merge settings, so readers arrive at a set of links into the documentation rather than at a static image.

The grid is not built when you generate. The cards are assembled in the reader's browser from the same table of contents data the menu uses, as soon as the help set's parcels have loaded:

• A Merge Settings container becomes a card, and the groups inside that container become the card's member links.

• A group that is not inside a container becomes a card of its own, and the first level of that group's table of contents becomes its member links.

• Every card offers at least one link. A container has no page of its own, and a group's own link is replaced when its parcel's table of contents is grafted into the tree, so wherever a card or member has no link of its own, the first link beneath it is used instead. A card that cannot reach any link is left out of the grid.

• A federated help set — a shell that assembles parcels published separately — fills its grid the same way, from the parcel data the shell loads in the browser.

The grid fits as many card columns as the page width allows, narrows to a single column on a phone in portrait orientation, and follows the same wide and narrow layout modes as the rest of the help set.

Because the grid reads the table of contents data, ePublisher includes that data in each generated parcel whenever the splash page is in use, not only when the menu's table of contents is generated. Only a target that has Generate table of contents disabled and Use first document as splash page enabled — no menu table of contents and no splash page — leaves the data out.

Note: WebWorks Reverb 2.0 no longer displays a splash image, and the format no longer references a splash.png file. An existing Pages\images\splash.png override in a project has no effect on the generated output; it is simply ignored. To keep a branded image on the splash page, override the Splash.asp page template instead, as described in Modifying the Splash Page.

To migrate a splash image override to the Groups Grid

1. In your Stationery design project, on the View menu, click Project Directory. For more information about override files and locations, see Stationery, Projects, and Overrides.

2. Look for a splash.png file in the Formats\WebWorks Reverb 2.0\Pages\images folder and in each Targets\<Target Name>\Pages\images folder in your project, where <Target Name> is the name of a specific target.

3. Delete each splash.png override you find, or move it somewhere outside the project. The file is no longer used, and leaving it in place makes the project look as though it still carries a customization.

4. If the grid alone is the presentation you want, adjust its appearance with the SASS variables described in Styling the Groups Grid, and stop here.

5. If you want to keep a branded image on the splash page, override Splash.asp and add your image above or below the grid container, as described in Modifying the Splash Page.

6. Regenerate your project to review the changes.